Conversation
fix problem with last line, for more info regarding this problem see this link: https://stackoverflow.com/questions/61055324/docker-cannot-execute-binary-file add slack channel software fix in this file at line 63, update sdk version 4.0->4.1
|
ok. In cuda12 docker file it also has the same issue. I will commit again
for both file. Thank you for checking this branch out.
Harish Kumar Balaji ***@***.***>于2025年2月12日 周三下午9:13写道:
… ***@***.**** commented on this pull request.
------------------------------
In setup/Dockerfile.cuda11.8
<#106 (comment)>:
> \ No newline at end of file
+ENTRYPOINT [ "/bin/bash", "-l", "-c" ]
Yes as your message suggests, if we are going to run any command at the
entry point, like starting the rosmaster using /bin/bash -c roscore then
we can use -c. Here we are not running any command at startup. We are
just starting the bash terminal so /bin/bash is enough. -c is of no use
as we are not going to run any command at the entry point.
Assuming you are in a professional place, in a company, it will be best
practice to remove the code when it is not useful.
You can keep the -l as it seems to be a best practice. Thanks for that.
—
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7VQYIHOO4GE4RZV345LIMT2PQEUPAVCNFSM6AAAAABXALIMQKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDMMJTG4ZDEMZQHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@RuimingShen Cuda 12 docker is tested in my local. It is working as expected. Please make the changes on the Cuda11 docker file and make sure to test it. |
|
ok
Harish Kumar Balaji ***@***.***>于2025年2月12日 周三下午9:26写道:
… ok. In cuda12 docker file it also has the same issue. I will commit again
for both file. Thank you for checking this branch out. Harish Kumar Balaji
*@*.
*>于2025年2月12日 周三下午9:13写道: … <#m_-9166376026741143802_> @.** commented on
this pull request. ------------------------------ In
setup/Dockerfile.cuda11.8 <#106 (comment)
<#106 (comment)>>:
> \ No newline at end of file +ENTRYPOINT [ "/bin/bash", "-l", "-c" ] Yes
as your message suggests, if we are going to run any command at the entry
point, like starting the rosmaster using /bin/bash -c roscore then we can
use -c. Here we are not running any command at startup. We are just
starting the bash terminal so /bin/bash is enough. -c is of no use as we
are not going to run any command at the entry point. Assuming you are in a
professional place, in a company, it will be best practice to remove the
code when it is not useful. You can keep the -l as it seems to be a best
practice. Thanks for that. — Reply to this email directly, view it on
GitHub <#106 (comment)
<#106 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7VQYIHOO4GE4RZV345LIMT2PQEUPAVCNFSM6AAAAABXALIMQKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDMMJTG4ZDEMZQHA
. You are receiving this because you authored the thread.Message ID: *@*
.***>
@RuimingShen <https://github.com/RuimingShen> Cuda 12 docker is tested in
my local. It is working as expected. Please make the changes on the Cuda11
docker file and make sure to test it.
—
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7VQYIF2NAZPRZFMCHMXO7D2PQGIHAVCNFSM6AAAAABXALIMQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJVGM3TCMRZGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|




fix problem with last line, for more info regarding this problem see this link: https://stackoverflow.com/questions/61055324/docker-cannot-execute-binary-file add slack channel software fix in this file at line 63, update sdk version 4.0->4.1